fix: add explicit TypeScript parser to prevent XML plugin conflicts #125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The
@prettier/plugin-xmlplugin in Prettier 3.6.0+ incorrectly identifies TypeScript files as XML, causing parsing errors during the post-install formatting step.Error details:
npx prettier --writepost-install step.scripts/lint.ts,src/bundleEntry.ts,src/main.tsSolution
Add explicit TypeScript parser configuration in
prettier.config.mjsoverrides to ensure.tsfiles are correctly identified and parsed.Testing
npx isaacscript@latest initcompletes successfullynpx prettier --writeruns without errorsImpact
Fixes broken initialization flow for new projects using the latest Prettier version while maintaining compatibility with all existing plugins.